Providing an integrated, feature oriented ad-hoc printing device selection system for mobile client devices

ABSTRACT

An integrated printer driver includes the capability to discover available ad-hoc printing devices and obtain the features and options currently supported by those ad-hoc printing devices. The integrated printer driver automatically selects a particular ad-hoc printing device based upon a user&#39;s selected feature and option set and allows a user to print an electronic document prior to an ad-hoc communications link being established with the particular ad-hoc printing device. The integrated printer driver renders the electronic document and generates a print job, and holds the print job until an ad-hoc communications link is established with the particular ad-hoc printing device. After the ad-hoc communications link has been established, the integrated printer driver determines whether the particular ad-hoc printing device is capable of successfully processing the print job and if so, causes the print job to be transmitted to the ad-hoc printing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No.11/830,129 (Attorney Docket 49986-0626), filed Jul. 30, 2007, issued asU.S. Pat. No. 8,508,755 on Aug. 13, 2013 and U.S. patent applicationSer. No. 13/333,454 (Attorney Docket 49986-0736), filed Dec. 21, 2011,the entire contents of both which are hereby incorporated by referencefor all purposes as if fully set forth herein.

FIELD OF THE INVENTION

The present invention relates to printing on ad-hoc printing device and,more particularly, to an approach for providing an integrated printerdriver than can print to multiple ad-hoc printing devices.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

A device driver or software driver is a computer program allowinghigher-level computer programs to interact with a hardware device. Inthe printing context, a printer driver allows applications (e.g.,Microsoft Word, Adobe Acrobat, SmartDraw, etc.) to print to a printingdevice without the applications being required to know the technicaldetails of the printing device. A printer driver converts applicationdata, from an application, to a form specific to a particular printingdevice.

Current printer drivers are printer specific, requiring that a separateprinter driver be manually installed, on each client device, for eachprinting device that a user wishes to print to. The user must know theexact printer model and then download a printer driver from themanufacture for that exact model. In addition, most printer drivers donot have dynamic feature support and therefore must be updated if anychanges are made to the printing devices. Some universal printer driversexit that provide limited dynamic feature support by defining a limitedset of features and then turning some features on or off through SNMPdevice querying. If a user moves their computing device (e.g., laptop)so that the computing devices is in a different network and the userdesires to be able to print to printing devices in that differentnetwork, then the user must add more printer drivers to their computingdevice. As a result of installing numerous printer drivers, the usermust retrieve all necessary printer information from every installedprinter driver. Thus, creating a simple print job can quickly become acomplicated job and result in an unfavorable user experience.Additionally, under current printer driver architectures, each printerdriver displays its own user interface (UI). If user selects a differentprinting device, then an operating system must open a new printer driverwith a different UI for that printing device.

Some current printer drivers are considered “universal” drivers in thatsuch drivers support multiple models. However, one universal driver canonly support one device at any given time. When multiple printingdevices are present on one network, multiple instances of universaldrivers must be installed into the operating system of a client device.

As a consequence of current printer driver architectures, if a userdesires to use a printer feature (such as hole punching) and the userdoes not know which printing device supports that printer feature, thenthe user must open each printer driver's UI in order to determine whichprinting device is capable of that printer feature.

Some printing devices, referred to herein as “ad-hoc printing devices,”now support ad-hoc wireless communications. Ad-hoc printing devices maybe very convenient in many situations. For example, ad-hoc printingdevices may be installed in locations such as shopping malls and coffeeshops to allow users to print “on-the-go” from mobile computing devices,such as smart phones, tablet computers, laptop computers, personaldigital assistants, etc. To print to an ad-hoc printing device, a usertypically moves a mobile client device in close proximity to aparticular ad-hoc printing device and establishes an ad-hoccommunications link between the user's mobile client device and theparticular ad-hoc printing device. After the ad-hoc communications linkhas been established, the user installs printer driver for thisparticular model, then the user prints and sends electronic document tothe particular ad-hoc printing device.

Despite the conveniences provided by ad-hoc printing devices, thereexist some drawbacks to using them. First, all of the issues describedabove with non-ad-hoc printing devices apply to ad-hoc printing devices.In addition, an ad-hoc communications link must be maintained untilprinting is completed. If a mobile client device is moved out of rangeof an ad-hoc printing device before a print job is completed, then theprint job may abort with an error. When this occurs, the user mustre-submit the entire print job to the ad-hoc printing device or locateanother ad-hoc printing device. Another issue is that ad-hoccommunications links are temporary and if a user wishes to print anotherelectronic document to the same ad-hoc printing device after the ad-hoccommunications link has been terminated, the user must first establish anew ad-hoc communications link to the ad-hoc printing device.

SUMMARY

According to an approach for printing from mobile client devices toad-hoc printing devices, prior to an ad-hoc wireless communications linkbeing established between a mobile client device and a particular ad-hocprinting device, at the mobile client device a print job is generated.After the ad-hoc wireless communications link is established between themobile client device and the particular ad-hoc printing device, adetermination, at the mobile client device, is made whether the printjob is compatible with the particular ad-hoc printing device. Inresponse to determining, at the mobile client device, that the print jobis compatible with the particular ad-hoc printing device, then the printjob is transmitted to the particular ad-hoc printing device via thead-hoc wireless communications link. In response to determining, at themobile client device, that the print job is not compatible with theparticular ad-hoc printing device, then at the mobile client device, anupdated print job is generated by resolving one or moreincompatibilities between the print job and the particular ad-hocprinting device. The updated print job is transmitted to the particularad-hoc printing device via the ad-hoc wireless communications link.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a block diagram that depicts an example ad-hoc printing devicefeature and option selection system.

FIG. 2 is a flow diagram that depicts an example process for generatinga print job.

FIG. 3 is a block diagram that depicts example components of anintegrated printer driver and a print server and the interaction ofthose components with respect to ad-hoc printing devices.

FIG. 4 is a block diagram that depicts a data flow of printing deviceinformation from multiple ad-hoc printing devices to a print server.

FIG. 5A is a block diagram that depicts an overview of a process foradding new ad-hoc printing devices.

FIG. 5B is a flow diagram that depicts a process for adding an ad-hocprinting device to a print server.

FIG. 6 is a sequence diagram that depicts a process for creating userinterface data.

FIG. 7 is a block diagram that depicts an overview of a process forprinting from a mobile client device to an ad-hoc printing device.

FIG. 8 is a sequence diagram that depicts a process for printing from amobile client device to an ad-hoc printing device.

FIG. 9 is a flow diagram that depicts a process for printing from amobile client device to a printing device.

FIG. 10 includes a flow diagram and a block diagram that depict aprocess for querying a new printing device that is being added to aprinter server.

FIG. 11 is a block diagram that depicts a data flow of generic printerdescription data (GPDD) after querying a new printing device.

FIG. 12 is a block diagram that depicts multiple versions of genericprinter description data in integrated feature selection printerdrivers.

FIG. 13 is a block diagram that depicts example generic printerdescription data for each of a server, a driver, and a user interface.

FIG. 14 is a flow diagram that depicts a process for a user changing afilter preference.

FIG. 15 is a flow diagram that depicts a process for a user changing afeature/option on a user interface (UI) of a printer driver.

FIG. 16 is a block diagram that depicts a job ticket that is generatedfrom an integrated user interface (UI).

FIG. 17 is a block diagram that depicts a printer selection preferencemenu.

FIG. 18 is a block diagram that depicts an example user interface thatallows a user to select one or more features and options for a printjob.

FIG. 20 is a block diagram that illustrates a computer system upon whichan embodiment of the invention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

-   -   I. OVERVIEW    -   II. AD-HOC PRINTING FEATURE AND OPTION SELECTION SYSTEM    -   III. OVERVIEW OF PRINTING FROM A MOBILE CLIENT DEVICE TO AN        AD-HOC PRINTING DEVICE    -   IV. EXAMPLE PRINTER DRIVER COMPONENTS    -   V. PRINTING DEVICE INFORMATION DATA FLOW    -   VI. DISCOVERING AND ADDING NEW AD-HOC PRINTING DEVICES    -   VII. CREATING USER INTERFACE DATA    -   VIII. PRINTING FROM A MOBILE CLIENT DEVICE TO AN AD-HOC PRINTING        DEVICE    -   IX. QUERYING A NEW PRINTING DEVICE    -   X. DATA FLOW GENERIC PRINTER DESCRIPTION DATA    -   XI. MULTIPLE VERSIONS OF GPDD    -   XII. EXAMPLE GPDD    -   XIII. CHANGING A SELECTION FILTER PREFERENCE    -   XIV. CHANGING UI FEATURE/OPTION    -   XV. JOB TICKET CREATION    -   XVI. PRINTER SELECTION PREFERENCE MENU    -   XVII. EXAMPLE PRINTER DRIVER USER INTERFACE    -   XVIII. ESTABLISHING AN AD-HOC COMMUNICATIONS LINK    -   XIX. IMPLEMENTATION MECHANISMS

I. Overview

An approach is provided for printing from mobile client devices toad-hoc printing devices. An integrated printer driver provides a single,combined user interface for printing to multiple ad-hoc printingdevices. The integrated printer driver includes the capability todiscover available ad-hoc printing devices and obtain the features andoptions currently supported by those ad-hoc printing devices. Theintegrated printer driver provides a unified, feature-oriented userinterface for the ad-hoc printing devices that allows a user to specifyfeatures and options for printing an electronic document. The integratedprinter driver automatically selects a particular ad-hoc printing devicebased upon the user's selected feature and option set. The integratedprinter driver allows a user to print an electronic document prior to anad-hoc communications link being established with the particular ad-hocprinting device. The integrated printer driver renders the electronicdocument and generates a print job, and holds the print job until anad-hoc communications link is established with the particular ad-hocprinting device. After the ad-hoc communications link has beenestablished, the integrated printer driver determines whether theparticular ad-hoc printing device is capable of successfully processingthe print job. According to one embodiment, this includes determiningwhether features and options specified for the print job, for examplevia a corresponding print ticket, are currently supported by the ad-hocprinting device. If so, then the integrated printer driver causes theprint job to be transmitted to the ad-hoc printing device. If not, thenthe integrated printer driver provides a user interface that allows auser to resolve any conflicts, for example, by changing one or morefeatures and options specified for the print job. If the print jobcannot be successfully processed by the ad-hoc printing device, forexample because of an error on the ad-hoc communications link or at thead-hoc printing device, the integrated printer driver allows a user tore-submit the print job to the same ad-hoc printing device or redirect,i.e., submit, the print job to a different ad-hoc printing device. Thisapproach provides a flexible and user-friendly experience for printingfrom mobile client device to ad-hoc printing devices.

II. Ad-Hoc Printing Feature and Option Selection System

FIG. 1 is a block diagram that depicts an example ad-hoc printing devicefeature and option selection system 100, according to an embodiment.System 100 includes mobile device clients 102, 104, 106, (102-106)communicatively coupled to ad-hoc printing devices 108, 110, 112, 114(108-114) and a print server 116 via one or more communications links118. The communications links 118 may include a wide variety ofcommunications links that may vary depending upon a particularimplementation and the approaches described herein are not limited toany particular types of communications links. Example communicationslinks include, without limitation, one or more wired or wirelessnetworks. The elements depicted in FIG. 1 may also communicate via anynumber of direct communications links between the elements. In theexample depicted in FIG. 1, ad-hoc communications links are establishedwith ad-hoc printing devices 108-114. The approaches described hereinfor printing from mobile client devices to ad-hoc printing devices mayuse a wide variety of ad-hoc communications links that may varydepending upon a particular implementation and the approaches are notlimited to any particular type of ad-hoc communications links. In theexample depicted in FIG. 1, an ad-hoc wired connection is establishedwith ad-hoc printing device 108, a WiFi direct connection 122 isestablished with ad-hoc printing device 110, a near field communicationconnection 124 is established with ad-hoc printing device 112 and a WiFiconnection 126 is established with ad-hoc printing device 114. Thesead-hoc communications links are provided as examples and the approachesdescribed herein are not limited to these example ad-hoc communicationslinks and are applicable to other types of ad-hoc communications links.

Mobile client devices 102-106 may be any type of mobile client devicethat may vary depending upon a particular implementation and theapproaches described herein are not limited to any particular type ofmobile wireless device. Example mobile wireless devices include, withoutlimitation, personal computers, workstations, laptop computers, tabletcomputing devices, personal digital assistants, smart phones and othertelephony devices. Mobile client devices 102-106 each include anintegrated printer driver 128, 130, 132, respectively, that isconfigured to providing printing to ad-hoc printing devices 108-114, asdescribed in more detail hereinafter. Although embodiments are describedherein in the context of three mobile printing devices (102-106), theapproaches described herein are applicable to any number and types ofmobile printing devices.

Ad-hoc printing devices 108-114 may be any type of device that includesprinting functionality. Ad-hoc printing devices 108-114 are not limitedto printers per se and may include printing devices that include otherfunctionality. Examples of ad-hoc printing devices 108-114 include,without limitation, printers, copiers and multi-function peripherals(MFPs).

Print server 116 is a network service that obtains printing devicecapabilities data from ad-hoc printing devices 108-114. Print server 116is depicted in FIG. 1 as a separate element for explanation purposesonly and print server 116 may be implemented on a stand-alone computingelement, such as a server, or on mobile client devices 102-106. Thefunctionality of print server 116 may be implemented using storedprogram logic, in a special-purpose computer or loaded from one or morenon-transitory media into the memory of a general-purpose computer andthen executed. Printing device capabilities data is data that specifiesthe features and options, i.e., allowed values for each feature,currently supported by ad-hoc printing devices 108-114. Examplesfeatures include, without limitation, a paper tray, duplex printing,stapling, hole punching, etc. Each feature has one or more options,i.e., values. Some features may only have two options. For example,duplex printing has two options, such as “Installed” or “Not Installed.”Other features, for example, paper size, may have many options, e.g.,“A4”, “legal”, “8½×11”, etc.

Embodiments are not limited to any particular technique for print server116 obtaining printing device capabilities data from ad-hoc printingdevices 108-114. For example, print server 116 may use SNMP or WSDtechnologies to obtain printing device capabilities data from ad-hocprinting devices 108-114. Recent development of WSD technologies on anetwork provides opportunities for more advanced device management(e.g., relative to SNMP). Such development allows any network device toreport its full (e.g., printing) capabilities during the establishmentof a connection between the network device and another network device,such as a network server. Print server 116 may itself automaticallydiscover ad-hoc printing devices 108-114 via, for example, a devicediscovery technique. Alternatively, print server 116 may be notified ofone or more of ad-hoc printing devices 108-114 by an administrator. Upondetection, print server 116 queries the detected ad-hoc printing devices108-114 (local or remote) for information about the ad-hoc printingdevices 108-114 including, but not limited to, print features andoptions and other capabilities supported by the ad-hoc printing devices108-114.

Based on the printing device capabilities data, print server 116 causesthe integrated printer drivers 128-132 to be generated and provided tomobile client devices 102-106. Additionally or alternatively, printserver 116 causes the printing device capabilities data to betransmitted to mobile client devices 102-106 that (already) execute theintegrated printer drivers 128-132 at the time print server 116 receivesthe device capabilities data from ad-hoc printing devices 108-114. Inthis situation, integrated printer drivers 128-132 are updated toinclude the new printing device capabilities data.

Print server 116 builds an information database and creates various datastructures for integrated printer drivers 128-132. Such data structuresmay be accessed by UI components of integrated printer drivers 128-132when integrated printer drivers 128-132 display an integrated UI to auser of one of mobile client devices 102-106.

After integrated printer drivers 128-132 are received by and installedat mobile client devices 102-106, integrated printer drivers 128-132display an integrated UI that contains features from multiple ad-hocprinting devices (e.g., ad-hoc printing devices 108-114). Some featureson the UI are automatically enabled or disabled based on a feature set auser has previously selected and whether any ad-hoc printing devices cansupport the selected feature set. Based on the feature set of the user'sselection, integrated printer drivers 128-132 determines which ad-hocprinting device 108-114 will be used for printing and saves the featureset to a destination print job ticket. A rendering component ofintegrated printer driver 128-132 causes a print job to be transmittedto an ad-hoc printing device (e.g., ad-hoc printing devices 108-114)specified in the print ticket.

III. Overview of Printing from a Mobile Client Device to an Ad-HocPrinting Device

FIG. 2 is a flow diagram that depicts an example process 200 forgenerating a print job, according to an embodiment. At step 202, ad-hoccommunications links are established with ad-hoc printing devices. Forexample, ad-hoc communications links may be established between mobileclient device 102 and any of ad-hoc printing devices 108-114. This mayinclude, for example, a user moving mobile client device 102 withinrange of and pairing the mobile client device 102 with ad-hoc printingdevices 108-114. In step 204, printing device capabilities data isobtained from the ad-hoc printing devices 108-114 for which an ad-hoccommunications link has been established. This may include, for example,the integrated printer driver 128 and/or print server 116, querying thead-hoc printing devices 108-114 to obtain printing device capabilitiesdata that specifies features and options currently supported by thead-hoc printing devices 108-114. Databases maintained by print server116 and/or mobile client devices 102-106 are also updated, as describedin more detail hereinafter.

In step 206, a user initiates printing of an electronic document frommobile client device 102 and integrated printer driver 128 displays auser interface of printing features and options. At step 208, the userselects printing features and options to be used to print the electronicdocument. At step 210, integrated printer driver 128 selects aparticular ad-hoc printing device to print the electronic document andthe user confirms the selected ad-hoc printing device. In step 212, theprint job is held, i.e., not rendered, until the selected ad-hocprinting device is connected, i.e., until an ad-hoc communications linkis established with the selected ad-hoc printing device.

Once the ad-hoc communications link is established with the selectedad-hoc printing device, then in step 214, the current features andoptions supported by the selected printing device are obtained and theprint job ticket is validated. This may include, for example, theintegrated printer driver 128 and/or print server 116, querying theselected ad-hoc printing device to obtain printing device capabilitiesdata that specifies features and options currently supported by theselected ad-hoc printing devices and comparing those features andoptions to the features and options specified by the print job ticket.

In step 216, one or more conflicts or inconsistencies between thefeatures and options specified by the print job ticket and the featuresand options that are currently supported by the selected ad-hoc printingdevice are resolved. This may include, for example, the integratedprinter driver 128 displaying, on a user interface, data that identifiesthe conflicts or inconsistencies and allows the user to change one ormore features and options specified for the print job to resolve theconflicts. For example, suppose that when the features and options forthe selected ad-hoc printing device were originally obtained that theselected ad-hoc printing device supported color printing. Supposefurther that the user had requested that the electronic document beprinted using color printing and that the selected printing device waschanged to no longer support color printing. Steps 214 and 216 providefor detection and resolution of this conflict, for example, by the userselecting black and white printing for the electronic document or by theuser selecting another ad-hoc printing device. In step 218, the printjob is generated, e.g., rendered, and transmitted to the selectedprinting device.

IV. Example Printer Driver Components

FIG. 3 is a block diagram that depicts example components of integratedprinter driver 128 and print server 116 and the interaction of thosecomponents with respect to ad-hoc printing devices 302-306. Print server116 includes device information databases 316-320, one for each ofad-hoc printing devices 302-306. Thus, device information database 316stores ad-hoc printing device capabilities data for ad-hoc printingdevice 302, device information database 318 stores ad-hoc printingdevice capabilities data for ad-hoc printing device 304 and deviceinformation database 320 stores ad-hoc printing device capabilities datafor ad-hoc printing device 306. Device information databases 316-320 aredepicted separately in FIG. 3 for purposes of explanation only and theinformation in device information databases 316-320 may be stored in asingle information database on one or more computing devices, dependingupon a particular implementation.

Print server 116 communicates with ad-hoc printing devices 302-306 viaad-hoc communications links, such as WiFi, NFC or WiFi Directcommunications links as depicted in FIG. 3. Print server 116 retrieves,from ad-hoc printing devices 302-306, ad-hoc printing devicecapabilities data that indicates the features and options currentlysupported by ad-hoc printing devices 302-306. The ad-hoc printing devicecapabilities data may be retrieved using a wide variety of techniquesthat may vary depending upon a particular implementation. Exampletechniques include, without limitation, Web Services Discovery and SNMPqueries. Integrated printer driver 128 includes an integrated UIcomponent 308, a driver update component 310, a rendering component 312a and an ad-hoc printing device manager 314. Integrated UI component 308generates a graphical user interface (GUI) and causes the GUI to bedisplayed on a user interface of the client device upon which integratedprinter driver 128 is installed, for example mobile client devices102-106. Driver update component 310 is configured to obtain ad-hocprinting device capability data from print server 116 for one or more ofad-hoc printing devices 302-306. Rendering component 312 receivesfeature selections (whether user selected, default, or a combination ofboth), selects an ad-hoc printing device to print and electronicdocument, and generates a print job that specifies the one or moredocuments and the feature selections. Rendering component 312 passes theprint job to ad-hoc printing device manager 314.

Ad-hoc printing device manager 314 is configured to query ad-hocprinting devices 302-306 for ad-hoc printing device capability data.Ad-hoc printing device manager 314 is also configured to causing printjobs to be transmitted to the appropriate ad-hoc printing devices.Ad-hoc printing device manager 314 may implement one or morecommunication protocols in order to cause print job to be transmitted tothe appropriate ad-hoc printing device. For example, integrated printerdriver 128 may cause a first print job to be transmitted to ad-hocprinting device 302 via a Web Services Device port and integratedprinter driver 128 may cause a second print job to be transmitted toad-hoc printing device 304 via a TCP/IP port.

V. Printing Device Information Data Flow

FIG. 4 is a block diagram that depicts a data flow of printing deviceinformation from multiple ad-hoc printing devices 410A-D to a printserver 420, according to an embodiment. Each ad-hoc printing device410A-D provides a printing information (info) set to print server 420.For example, printing devices 410A-D provide printer information sets1-4, identified by reference numerals 412A-D, respectively, to printserver 420. Ad hoc printing devices 410A-D may communicate with printserver 420 using a wide variety of communication methods, such as USB(or Universal Serial Bus), WSD, wireless TCP, wired TCP, or theInternet. Although FIG. 4 depicts four ad-hoc printing devices 410A-D,embodiments are applicable to any number of ad-hoc printing devices.

Print server 420 receives printer information sets 412A-D and, in anembodiment, applies one or more filter criteria to printer informationsets 412A-D. The one or more filter criteria may be used to identifywhich ad-hoc printing devices are not allowed to be used (or “seen”) bymobile client devices that are connected to print server 420. In thisembodiment, print server 420 compares the one or more filter criteria toone or more attributes of an ad-hoc printing device (e.g., 410A), whichare reflected in a printer information set (e.g., 412A) received fromthat ad-hoc printing device. Example filter criteria include whether thead-hoc printing device supports a certain security policy or anysecurity, whether the ad-hoc printing device supports a particular pagedescription language (PDL), or any device with particular firmwareversions. Additionally or alternatively, one or more filter criteriaincludes a list of ad-hoc printing devices that are allowed to be usedby mobile client devices that are connected with print server 420 (e.g.,a “white” list) or a list of ad-hoc printing devices that are notallowed to be used by mobile client devices that are connected to printserver 420 (e.g., a “black” list). The one or more filter criteria maybe established by a company administrator, or an administrator that isauthorized by a business entity that owns and/or manages the localnetwork.

If an ad-hoc printing device is not “filtered out” after the filterstage, then print server 420 stores the printer information set of thatad-hoc printing device in an ad-hoc printer feature database 422. Thedata stored therein is referred to as the server generic printerdescription data (or “Server GPDD”). The Server GPDD, on a server when amobile client device is connecting to a corporate domain network, or onthe mobile client device when the mobile client device is disconnectedfrom a corporate domain network, defines information on all ad-hocprinting devices (whether connected or not connected) that are availablefor all users of that mobile client device.

In an embodiment, printer information sets of ad-hoc printing devicesthat are “filtered” out after the filter stage are stored separate fromthe Server GPDD. Such storage may be on the same storage device thatstores on the Server GPDD or on a different storage device. Such ad-hocprinter information sets may be maintained if, for example, the one ormore filter criteria are later changed or updated, for example throughuser input. In such a scenario, the “excluded” printer information setsmay be evaluated again based on the updated filter criteria. Such are-evaluation might be triggered based on the changing of the one ormore filter criteria. One or more of the excluded printer informationsets might then pass the filter stage and end up being stored as part ofthe Server GPDD.

In an embodiment, the Server GPDD may be further filtered based on oneor more additional filter criteria. Such additional criteria may beestablished by a driver administrator, who may be the same or differentthan the administrator that defines the filter criteria referencedabove. Examples of such additional filter criteria include thosecriteria described previously and whether a particular user is allowedto use a particular ad-hoc printing device, which may be determined inmultiple ways, such as a pre-defined list of ad-hoc printing devicesthat the particular user is allowed to use. The ad-hoc printerinformation sets of ad-hoc printing devices that are not “filtered out”by this additional filter criteria are referred to as “Driver GPDD.” TheDriver GPDD 424 defines information on all ad-hoc printing devices(whether connected or not) that are available for a particular user.Thus, each mobile client device that is communicatively coupled to (orregistered with) print server 420 might receive a different Driver GPDD.For example, the Server GPDD may include information only about ad-hocprinting devices 410A-C and not ad-hoc printing device 410D. Afterward,Driver GPDD 424 for one mobile client device might include informationonly about ad-hoc printing devices 410A-B while Driver GPDD 424 foranother mobile client device might include information only about ad-hocprinting devices 410A and 410C.

The Driver GPDD 424 of a particular user becomes part of an integratedprinter driver (whether generated by print server 420 or another entity)that is installed on a mobile client device of the particular user.

In an embodiment, the Driver GPDD 424 is further filtered by one or morefilter criteria that are defined by the associated user. For example,the associated user might indicate that they only want to seeinformation about ad-hoc printing devices that are on a particular floorof a building, that support color, and that have a certain input binsize. The printing information sets that satisfy the filter criteriadefined by the user will be part of a “UI GPDD” 426. The UI GPDD 426 fora particular user defines information on all connected ad-hoc printingdevices that are available for the particular user. The UI GPDD 426 maybe updated in real-time as the particular user makes selections aboutwhat characteristics or attributes a set of ad-hoc printing devices musthave in order to be candidate ad-hoc printing devices for print jobsthat are initiated by the particular user.

VI. Discovering and Adding New Ad-Hoc Printing Devices

A ad-hoc printing device is discovered and added to a print server whena print server obtains details about the ad-hoc printing device, such asan address (e.g., IP or MAC) of the ad-hoc printing device,communication protocol(s) that the ad-hoc printing device supports,physical location of the ad-hoc printing device (e.g., building number,floor level), and set of features and options that the ad-hoc printingdevice supports.

FIG. 5A is a block diagram that depicts an overview of a process foradding new ad-hoc printing devices, according to an embodiment. Anintegrated printer driver 502 includes a print server 504 that discoversand adds new ad-hoc printing devices 506, 508, 510. Note that in thisexample, print server 504 is depicted and described as being part ofintegrated printer driver 502, but embodiments are not limited to thiscontext and print server 504 may be implemented separate from integratedprinter driver 502. As depicted in FIG. 5, in Step 1, a user pairs, viaa local WSD connection, i.e., establishes ad-hoc communications linkswith, ad-hoc printing devices 506-510. In the present example, a WiFiconnection is established with ad-hoc printing device 506, a NFCconnection is established with ad-hoc printing device 508 and a WiFiDirect connection is established with ad-hoc printing device 510.

In Step 2, print server 504 discovers and queries ad-hoc printingdevices 506-510, as previously described herein. This may include theuse of a local WSD connection as depicted in FIG. 5. In Step 3, printserver 504 builds an ad-hoc printing device database, adds thediscovered ad-hoc printing devices 506-510 and updates the integratedprinter driver 502. In Step 4, a UI component 512 of the integratedprinter driver 502 displays devices features that are currentlysupported by the profiled ad-hoc printing devices 506-510, i.e., thead-hoc printing devices 506-510 that have been discovered by printserver 504 and for which print server 504 has obtained ad-hoc printingdevice capability data that specifies the current features and optionssupported by ad-hoc printing devices 506-510.

FIG. 5B is a flow diagram that depicts a process 550 for adding aconnected ad-hoc printing device to a print server, according to anembodiment. It is presumed that an ad-hoc communications link has beenestablished with the ad-hoc printing device. At step 552, a userprovides, to the print server, information about a new ad-hoc printingdevice. Example information includes, without limitation, a network IPaddress, an Internet IP address or a MAC address of the ad-hoc printingdevice. The ad-hoc printing device may be local to (i.e., on the samenetwork as) or remote to (i.e., not on the same network as) the printserver. Alternatively, the print server may automatically discover thenew ad-hoc printing device. Such automatic discovery may be achieved inmultiple ways. For example, upon an ad-hoc communications link beingestablished with the new ad-hoc printing device, the new ad-hoc printingdevice implements a Web Services Discovery specification by transmittinga HELLO multicast message to devices on the network. The print serverreceives the HELLO message, responds with a message that identifies theprint server. If both the print server and the new ad-hoc printingdevice implement a Web Services Metadata Exchange specification, thenthe print server sends a metadata request message to the new ad-hocprinting device in order to retrieve information about how to requestcertain information about the new ad-hoc printing device, such as ad-hocprinting device capabilities data.

At step 554, the print server queries the new ad-hoc printing device forcertain information, such as capabilities data of the ad-hoc printingdevice, any security protocols the ad-hoc printing device supports, etc.

At step 556, the print server applies an administrative policy to atleast some of the information retrieved from the ad-hoc printing device.The administrative policy indicates that the ad-hoc printing device mustsupport a particular PDL (or page description language), the ad-hocprinting device appears on a specified company list, and the ad-hocprinting device uses secure communication.

At step 558, the print server determines, based on the administrativepolicy, whether the ad-hoc printing device should be added to the ServerGPDD. If not, then process 500 proceeds to step 560, where the printserver causes a message to be displayed that indicates that the “add”operation is denied. If the print server determines that the ad-hocprinting device should be added to the Server GPDD, then process 500proceeds to step 562.

At step 562, the print server builds the Server GPDD database. This stepmay comprise adding the retrieved information about the new ad-hocprinting device to the Server GPDD database.

At step 564, the print server uses another policy to determine whetherthe new ad-hoc printing device should appear in a UI of a printerdriver. The other policy may be defined by a driver administrator anddetermines whether a mobile client device is able to “see” certainad-hoc printing devices. If the result of step 564 is in the negative,then process 500 proceeds to a point prior to step 552, indicating thatfurther input regarding a new ad-hoc printing device is required toproceed. If the result of step 564 is in the affirmative, then process500 proceeds to step 566.

At step 568, the print server rebuilds a Driver GPDD. This step maycomprise adding the retrieved information about the new ad-hoc printingdevice to a Driver GPDD.

At step 570, the print server sends the retrieved information to anoperating system of a mobile client device that executes a printerdriver. At step 570, the operating system updates the printer driverbased on the retrieved information. Alternatively, a user might decideto update the driver at a later time.

VII. Creating User Interface Data

FIG. 6 is a sequence diagram that depicts a process 600 for creatinguser interface data, according to an embodiment. An ad-hoc printingdevice 610 receives, from an administrator, ad-hoc printing deviceinformation. Example information includes, without limitation, a name ofa company that owns ad-hoc printing device 610 and location of ad-hocprinting device 610, such as a building number, floor, section,department name, maintenance group name, etc. Such information might bereceived before ad-hoc printing device 610 is installed. Suchinformation depends on user's input, not the device's nativeinformation. Also, such information may be received through a devicecontrol panel of ad-hoc printing device 610.

At step 1, a print server 620 sends one or more queries to ad-hocprinting device 610 to request information about ad-hoc printing device610, including capabilities of ad-hoc printing device 610. One or moretechniques may be used to send the one or more queries, including, butnot limited to, WS Discovery queries, an OS network API, SNMP queries,etc.

At step 2, ad-hoc printing device 610 returns, to print server 620, theinformation that print server 620 requested.

At step 3, print server 620 checks one or more company or domainadministrative policies and builds (or rebuilds) a Server GPDD based onthe retrieved information.

At step 4, print server 620 checks a user policy and builds (orrebuilds), based on the retrieved information, a Driver GPDD for eachuser that is authorized to use ad-hoc printing device 610.

At step 5, print server 620 sends the retrieved information to the OSabout updating each printer driver user that is authorized to use thead-hoc printing device. The OS, in turn, notifies a driver updatecomponent 630 that is part of the printer driver. Driver updatecomponent 630 updates the driver's UI data. If a driver UI component ofthe printer driver is already processing a print job, then driver updatecomponent 630 might include adequate solutions to ensure that the new UIupdate does not affect existing print jobs.

At step 6, driver update component 630 might broadcast, to one or moreapplications 640 executing on the client device, a message that a new UIwill be used. For some printing applications, it is important to informthe user that one or more ad-hoc printing device properties havechanged, such as when a staple unit is removed. A user should benotified to avoid sending print jobs that require the staple unit.

VIII. Printing from a Mobile Client Device to an Ad-Hoc Printing Device

FIG. 7 is a block diagram 700 that depicts an overview of a process forprinting from a mobile client device to an ad-hoc printing device. InFIG. 7, an integrated print driver 702 is implemented on a mobile clientdevice (not shown) and interacts with ad-hoc printing devices 704, 706,708. Integrated print driver 702 includes a UI component 710, arendering component 712 and a print server 714. In this example printserver 714 is implemented as part of integrated printer driver 702 forpurposes of explanation but embodiments are not limited to this exampleand print server 714 may be implemented separate from integrated printdriver 792.

In Step 1, a user initiates a print job with a job ticket via UIcomponent 710. This may include, for example a user requesting to printa particular electronic document on a particular ad-hoc printing device,referred to in this example and depicted in FIG. 7 as the “target ad-hocprinting device,” and selecting, via UI component 710, features andoptions to be used to print the particular electronic document. Theprint job and print job ticket are provided to rendering component 712.

In Step 2, rendering component 712 holds the print job until an ad-hoccommunications link is established with the target ad-hoc printingdevice that was specified by the user. In Step 3, the user establishesan ad-hoc communications link with the target ad-hoc printing device.This may include, for example, a user moving the mobile client deviceinto close proximity of the target ad-hoc printing device and initiatingan ad-hoc communications link with the target ad-hoc printing device,e.g., pairing the mobile client device to the target ad-hoc printingdevice. In Step 4, the user's mobile client device detects that thead-hoc communications link has been established between the mobileclient device and the target printing device.

In Step 5, in response to the ad-hoc communications link beingestablished between the mobile client device and the target printingdevice, print server 714 queries the target ad-hoc printing device toobtain ad-hoc printing device capability data that specifies thefeatures and options currently supported by the target ad-hoc printingdevice. Print server 714 compares the features and options currentlysupported by the target ad-hoc printing device to the features andoptions specified in the print job ticket to determine whether anyconflicts exist, i.e., whether the target ad-hoc printing devicecurrently supports the features and options necessary to process theprint job. It is presumed in this example that print server 714 hasaccess to the print job ticket for the print job. If any conflictsexist, then print server 714 causes UI component 710 to display one ormore GUI objects that allow the user to resolve the conflicts, forexample, by changing one or more of the features and options to be usedto print the print job.

In Step 6, after any conflicts are resolved by the user, the print jobis allowed to be processed by rendering component 712.

FIG. 8 is a sequence diagram 800 that depicts a process for printingfrom a mobile client device to an ad-hoc printing device, according toan embodiment. It is presumed in this sequence for purposes ofexplanation that a print server has discovered one or more availablead-hoc printing devices and has obtained, from those ad-hoc printingdevices, ad-hoc printing device capability data that specifies featuresand options supported by those ad-hoc printing devices. In Step 1, aUser initiates a print job via a printer driver UI component. This mayinclude, for example a user requesting to print a particular electronicdocument on a particular ad-hoc printing device, referred to in thisexample as the “target ad-hoc printing device,” and selecting, via theprinter driver UI component, features and options to be used to printthe particular electronic document. The information input by the uservia the printer driver UI component is provided to an ad-hoc printingdevice manager.

In Step 2, the Ad-Hoc Printing Device Manager prompts the user, via theprinter driver UI component, to establish an ad-hoc communications linkbetween the mobile client device and the target ad-hoc printing device,for example, by pairing the mobile client device with the target ad-hocprinting device.

In Step 3, the user establishes an ad-hoc communications link betweenthe mobile client device and the target ad-hoc printing device, forexample, by pairing the mobile client device with the target ad-hocprinting device. After the ad-hoc communications link has beenestablished, then in Step 4, the print server again queries the targetad-hoc printing device for ad-hoc printing device capability data thatspecifies the current features and options supported by the targetad-hoc printing device. This is performed because the features andoptions currently supported by the target ad-hoc printing device mayhave changed since the ad-hoc printing device capability data waspreviously acquired from the target ad-hoc printing device.

In Step 5, the print server determines whether any conflicts existbetween the print job and the target ad-hoc printing device. Accordingto one embodiment, the print server compares the features and optionscurrently supported by the target ad-hoc printing device to the featuresand options specified in the print job ticket to determine whether anyconflicts exist, i.e., whether the target ad-hoc printing devicecurrently supports the features and options necessary to process theprint job. If any conflicts exist, then the print server causes theprinter driver UI component to display one or more GUI objects thatallow the user to resolve the conflicts, for example, by changing one ormore of the features and options to be used to print the print job. InStep 6, the user resolves any conflicts between the print job ticket andthe features and options currently supported by the target ad-hocprinting device and processing of the print job continues. In Step 7,the ad-hoc printing manager causes the rendering component to render theprint data to be rendered by the rendering component. In Step 8, thead-hoc printing device manager causes the print job to be sent to thead-hoc printing device.

FIG. 9 is a flow diagram 900 that depicts a process for printing from amobile client device to a printing device, according to an embodiment.In Step 902, a user specifies features and options for processing printjob, for example, via a graphical user interface provided by a printdriver. In step 904, the print driver loops through all the features andoptions selected by the user and, in step 906, validates the selectedfeatures and options. In step 908, a print job ticket is generated, forexample, by the print driver.

In step 910, a determination is made whether more than one printingdevice currently supports the features and options specified in theprint job ticket. This may include ad-hoc printing device and non-ad-hocprinting devices. If there is only one printing device that currentlysupports the features and options specified in the print job ticket,then in step 912, that printing device is selected as the targetprinting device. If in step 910 a determination is made that there ismore one printing device that currently supports the features andoptions specified in the print job ticket, then in step 914, theprinting device that best supports the features and options specified inthe print job ticket is selected as the target printing device.

In step 916, a determination is made whether the target printing deviceis an ad-hoc printing device. If not, then in step 918, the print jobticket is sent to the rendering component. If, in step 916, adetermination is made that the target printing device is an ad-hocprinting device, then in step 920, a determination is made whether thetarget ad-hoc printing device is connected, i.e., whether an ad-hoccommunications link is established between the mobile client device andthe target ad-hoc printing device. If not, then in step 922, the user isprompted to establish an ad-hoc communications link between the user'smobile client device and the ad-hoc printing device by, for example,pairing the user's mobile client device with the ad-hoc printing device.

If an ad-hoc communications link is established between the user'smobile client device and the ad-hoc printing device, then in step 924,the target ad-hoc printing device is queried to obtain the ad-hocprinting device capabilities data that specifies the features andoptions currently supported by the target ad-hoc printing device. Instep 926, a determination is made whether the features and optionsspecified by the ad-hoc printing device capabilities data conform to theprint job ticket. This indicates whether the target ad-hoc printingdevice is currently capable of processing the print job. If so, thencontrol proceeds to step 918 and the print job ticket is sent to therendering component. If not, then control returns to step 928 where theuser is given an opportunity to resolve any conflicting print ticketsettings. In step 930, the rendered print job is sent to the targetprinting device.

IX. Querying a New Printing Device

FIG. 10 includes a flow diagram and a block diagram that depict aprocess 1000 for querying a new printing device that is being added to aprinter server, such as print server 116, according to an embodiment.

At step 1005, a new printing device is added to a printer server. Thenew printing device may have been discovered automatically by theprinter server or a network administrator might have informed theprinter server about the new printing device, such as an IP or MACaddress of the new printing device.

At step 1010, the printer server queries the new printing device for aname to be used for the printing device. As indicated in Server GPDD1002, a name for the new printing device is “Ricoh MP C3300.”

At step 1015, the printer server queries the new printing device for alocation, such as building number and floor number. As indicated inServer GPDD 1002, the new printing device is on “Floor 1” of “Building1.”

At step 1020, the printer server queries the new printing device for adomain name. As indicated in Server GPDD 1002, the name of the domain ofthe new printing device is “Companyxxx.”

At step 1025, the printer server queries the new printing device for atype of connection of the new printing device to the printer server. Asindicated in Server GPDD 1002, the connection type is a wired network.

At step 1030, the printer server queries the new printing device forwired or wireless type. As indicated in Server GPDD 1002, the newprinting device is wired.

At step 1035, the printer server queries the new printing device for atype of printing security supported by the new printing device. In thisexample, the security printing type is not reflected in Server GPDD1002.

At step 1040, the printer server queries the new printing device for thedevice's type, such as whether the new printing device is a laserprinter or an inkjet printer. As indicated in Server GPDD 1002, the newprinting device is a laser printer.

At step 1045, the printer server queries the new printing device forwhether the new printing device supports color or just black and white.As indicated in Server GPDD 1002, the new printing device is a colorprinter.

At step 1050, the printer server queries the new printing device for theprinter's speed. As indicated in Server GPDD 1002, the new printingdevice is “Low.” Other possible values for speed might be “High” or“Medium” or may be a metric that reflects a speed, such as “100 sheetsper minute.”

At step 1055, the printer server queries the new printing device forinput bin size, which, in this example, is not reflected in Server GPDD1002.

At step 1060, the printer server queries the new printing device for oneor more printer features. As indicated in Server GPDD 1002, one featureof the new printing device is “Sides” whose display name is “Print onBoth Sides.” Also indicated in Server GPDD 1002 is the fact that the“Sides” feature has three options: “OneSided”, “TwoSidedLongEdge”, and“TwoSidedShortEdge”. Each of the three options is associated with acorresponding display name, such as “None”, “Flip on long edge” and“Flip on short edge”.

At step 1065, the printer server builds (or rebuilds) Server GPDD 1002to indicate the information that is retrieved in steps 1010-1060.

X. Data Flow Generic Printer Description Data

FIG. 11 is a block diagram that depicts a data flow 1100 of genericprinter description data (GPDD) after querying a new printing device,according to an embodiment. After retrieving information about a newprinting device (such as the information retrieved in steps 710-760described above), a printer server (e.g., print server 116 in FIG. 1)performs a check 1110. Check 1110 involves determining whether anadministrative policy allows the new printing device to be added to aServer GPDD 1120. This check may be performed prior to receiving allinformation about the new printing device, such as specific features andoptions. For example, after determining that a new printing device doesnot support any secured printing, then the printer server might notquery the new printing device for information about supported featuresand options.

If check 1110 results in the negative, then information about the newprinting device is discarded. If the check 1110 results in theaffirmative, then information about the new printing device is added toServer GPDD 1120. As indicated in FIG. 11, Server GPDD 1120 includes aGPDD tag that indicates a GPDD value, which is “Server Level” indicatinga server GPDD.

The printer server then performs check 1130, which involves determiningwhether an administrative policy allows the new printing device to beadded to a Driver GPDD 1140, which corresponds to a particular user or aparticular client device that is registered with the printer server. Asindicated in FIG. 11, Driver GPDD 1140 includes a GPDD tag thatindicates a GPDD value, which is “Driver Level” indicating a driverGPDD. If check 1130 results in the negative, then information about thenew printing device is not added to Driver GPDD. If check 1130 resultsin the affirmative, then information about the new printing device isadded to Driver GPDD 1140. As indicated in FIG. 11, Driver GPDD 1140includes a GPDD tag that indicates a GPDD value, which is “Driver Level”indicating a driver GPDD.

The printer server may perform check 1130 for each user that isregistered with the printer server or for each client device that isregistered with the printer server and, optionally, that includes anintegrated printer driver.

If check 1130 results in the affirmative, then the printer server sendsthe information about the new printing device to the client device thatis associated with Driver GPDD 1140. The printer driver executing onthat client device performs check 1150, which involves determiningwhether the new printing device is to be added to a list of availableprinting devices for the client device. If check 1150 results in thenegative, then a UI GPDD on the client device is not updated. If check1150 results in the affirmative, then the printer driver updates UI GPDD1160 to include information about the new printing device. As indicatedin FIG. 11, UI GPDD 1160 includes a GPDD tag that indicates a GPDDvalue, which is “UI Level” indicating a UI GPDD. Also, UI GPDD 1160includes a user tag that indicates a name value, which is “user1” inthis example.

XI. Multiple Versions of GPDD

FIG. 12 is a block diagram that depicts multiple versions of genericprinter description data in integrated feature selection printerdrivers, according to an embodiment. FIG. 12 depicts a printer server1210 and a Server GPDD database 1212. Printer server 1210 generates,based on Server GPDD in database 1212, a Driver GPDD and an integratedprinter driver for each registered user 1220A-C. For example, DriverGPDD 1222A and integrated printer driver 1224A is generated for user1220A; Driver GPDD 1222B and integrated printer driver 1224B isgenerated for user 1220B; and so forth. Each of Driver GPDD 1222A-C is asubset of the Server GPDD stored in database 1212.

Based on the Driver GPDD received at the corresponding client device, aprinter driver generates a UI GPDD. For example, printer driver 1224Agenerates UI GPDD 1230A based on Driver GPDD 1222A, printer driver 1224Bgenerates UI GPDD 1230B based on Driver GPDD 1222B, and so forth. Thus,each UI GPDD is a subset of its corresponding Driver GPDD.

From its UI GPDD, a printer driver generates a user interface on adisplay of a client device. For example, printer driver 1224A generatesUI 1232A based on UI GPDD 1230A, printer driver 1224B generates UI 1232Bbased on UI GPDD 1230B, and so forth.

XII. Example GPDD

FIG. 13 is a block diagram that depicts example generic printerdescription data for each of a server, a driver, and a user interface,according to an embodiment. FIG. 13 depicts an example Server GPDD 1310,an example Driver GPDD 1320, and an example UI GPDD 1330. Although GPDDs1310-1330 are in an XML format, embodiments of the invention are notlimited to GPDDs in an XML format. Alternative formats are possible.

In this example, each of GPDDs 1310-1330 include the same information ofa printing device, such as attributes of the printing device (e.g.,name, location, connection type, device type, etc.) and capabilitiesdata that includes options for the feature “Sides.” Also, each of GPDDs1310-1330 includes a different value for the GPDD Value. Specifically,Server GPDD 1310 indicates “Server level” as the value for the GPDDValue, Driver GPDD 1320 indicates “Driver level” as the value for theGPDD Value, and UI GPDD 1330 indicates “UI level” as the value for theGPDD Value.

XIII. Changing a Selection Filter Preference

FIG. 14 is a flow diagram that depicts a process 1400 for a userchanging a filter preference, according to an embodiment. Process 1400may be performed by one or more components or modules of a printerdriver, such as driver update module 334 depicted in FIG. 3.

At step 1410, a user changes a UI selection preference. Examples of UIselection preferences include, but are not limited to, location (e.g.,building number or floor number), IP address (e.g., a specific subnet),security information, and color or black/white. The user might changethe UI selection preference through a UI generated by a printer driver.As a result of performing step 1410, the printer driver might delete allUI GPDD and rebuild it using the following process. Alternatively, theprinter driver might delete, from a UI GPDD one at a time, onlyinformation about a printing device that the printer driver determinesshould not be included in the UI GPDD based on the user's selectionpreference.

At step 1420, the printer driver identifies a printing device indicatedin a Driver GPDD to which the printer driver has access. The Driver GPDDmay be stored on the same client device that executes the printerdriver.

At step 1430, the printer driver determines whether the printing deviceidentified in step 1420 should be displayed in a user interface that auser uses to select features and options for a particular print job.This determination may be made by comparing the current set of selectionpreferences with attributes/characteristics of the identified printingdevice or by comparing just the changed preference with suchattributes/characteristics. If step 1430 results in the negative, thenprocess 1400 proceeds to step 1440, where information about theidentified printing device is not included in (e.g., deleted from) theUI GPDD. If step 1430 results in the affirmative, then process 1400proceeds to step 1450.

At step 1450, the printer driver adds the printing device's capabilities(i.e., features and options) into a UI GPDD, from which the printerdriver eventually generates a user interface.

At step 1460, the printer driver determines whether information abouteach printing device indicated in the Driver GPDD has been analyzed. Ifnot, then process 1400 proceeds to step 1420. Otherwise, process 1400proceeds to step 1470.

At step 1470, the printer driver causes all (or many) features andoptions indicated in the updated UI GPDD to be re-displayed on theclient. Only the features and options of printing devices that areidentified in the UI GPDD are displayed. Thus, information about anyprinting devices that were not included in the UI GPDD in step 1450 isnot displayed to a user of a client device that executes the printerdriver.

At step 1480, one or more applications that are currently using thisprinter driver are notified, e.g., by the printer driver.

XIV. Changing UI Feature/Option

The selection of features and options under an integrated printer driverapproach is different compared to other printer drivers. To supportmultiple devices in one user interface, the integrated printer drivershould ensure that every feature set selection by a user is supported byat least one printing device. Constraints to features are appliedaccording to device support by any devices. In other words, if none ofthe printing devices indicated in a UI GPDD supports a particularfeature, then that particular feature appears disabled.

FIG. 15 is a flow diagram that depicts a process 1500 for a userchanging a feature/option on a user interface (UI) of a printer driver,according to an embodiment.

At step 1510, the UI receives, from a user, input that indicates achange in a feature or option. Examples of a change include changing thepaper size from 8.5×11 to A4, or changing the input bin, or requiringstapling.

At step 1520, the printer driver identifies a printing device indicatedin a Driver GPDD. If there is more than one printing device identifiedin the Driver GPDD, then the printer driver might “loop through” eachidentified printing device. In other words, steps 1520-1560 will beperformed for each identified printing device.

At step 1530, the printer driver determines whether the printing deviceidentified in step 1520 supports the feature/option selected in step1510. If not, then process 1500 proceeds to step 1540. If so, thenprocess 1500 proceeds to step 1550.

At step 1540, the printer driver disables all features of the printingdevice identified in step 1520 if the printing device does not supportthe feature/option set previously selected by user.

At step 1550, the printer driver enables all features for this printingdevice in the UI if the feature set previously selected by user issupported by the printing device.

At step 1560, the printer driver determines whether all printing deviceshave been identified in the Driver GPDD. If not, then process 1500proceeds to step 1520 to identify another printing device. Otherwise,process 1500 proceeds to step 1570.

At step 1570, for each feature enabled/disabled in the UI, the printerdriver enables or disables that feature in a UI GPDD. Thus, if feature 1is enabled in the UI, then the printer driver enables feature 1 in theUI GPDD. Conversely, if feature 2 is disabled in the UI, then theprinter driver disables feature 2 in the UI GPDD.

XV. Job Ticket Creation

FIG. 16 is a block diagram that depicts a job ticket 1620 that isgenerated from an integrated user interface (UI) 1610, according to anembodiment. Integrated UI 1610 is not necessarily what a user sees.Rather, integrated UI 1610 is a conceptual representation of differentfeatures and options that a user selected and of what printing devicessupport those features and options. For example, integrated UI 1610indicates three features: Color Mode, Staple, and Punch. The options forColor Mode are “Color” and “Gray Scale” where “Gray Scale” is selected(whether affirmatively selected by a user or a default selection). Theoptions for Staple are “OFF”, “Top Left”, and “Right 2” where “OFF” isselected. The options for Punch are “Left 2”, “Top 2”, and “Right 3”where “Left 2” is selected.

Integrated UI 1610 further indicates, for the “Color Mode” feature, thatPrinting Device 1 supports options “Color” and “Gray Scale” and thatPrinting Device 2 supports only the “Gray Scale” option. Integrated UI1610 indicates that Printing Device 2 supports the “Staple” feature. Forthe “Punch” feature, integrated UI 1610 indicates that Printing Device 2supports options “Left 2” and “Top 2” and that Printing Device 3supports options “Top 2” and “Right 3.”

As indicated in integrated UI 1610, only Printing Device 2 supports allthe selected features and options. Based on the options and featuresselected, the printer driver generates job ticket 1620. In this example,job ticket 1620 is an XML file that includes an element or tag for eachselected feature where the root element identifies a printing device. Inthis example, the value of the attribute “Device” in the “Job Ticket”element is “Device 2”, referring to Printing Device 2. The resultingprint job will thus be sent to Printing Device 2. Also, there are threeelements: “ColorMode”, “Staple”, and “Punch.”

The value of each element indicates the selected option for thecorresponding feature. In this example, the value of the “ColorMode”element is “Gray Scale”, the value of the “Staple” element is “OFF”, andthe value of the “Punch” element is “Left 2”.

XVI. Printer Selection Preference Menu

FIG. 17 is a block diagram that depicts a printer selection preferencemenu 1700, according to an embodiment. A printer driver (e.g.,integrated printer driver 128) might generate a display that is based onselections of one or more preferences indicated in menu 1700. Menu 1700indicates possible attributes or characteristics of printing devices.Menu 1700 allows a user to select different attributes that a set oftarget printing devices must have in order to be a candidate printingdevice to process future print jobs.

In this example, menu 1700 indicates possible locations of a printingdevice, possible domains of a printing device, whether a printing deviceis wired or wireless, whether a printing device is secured or not,whether a printing device is a laser or inkjet printer, whether aprinting device supports color or just black and white, whether theprinting device is a high speed or a low speed printer, whether aprinting device supports an input bin size of 500 sheets or just 100sheets, possible connection types of a printing device, and an option tobe on a user defined list. Initially, menu 1700 might include defaultselections, such as “Any” for each attribute/preference. Once a user isfinished making any selections, the final set of selectedattributes/preferences are used to determine which printing devices maybe used to process print jobs. A printer driver might use the selectionsto build (or rebuild) a UI GPDD that indicates a set of features andoptions that are supported by printing devices that satisfy thepreference selections indicated in menu 1700. A UI component of theprinter driver might generate a user interface based on the UI GPDD.

XVII. Example Printer Driver User Interface

FIG. 18 is a block diagram that depicts an example user interface 1800,according to an embodiment. User interface 1800 may be generated by a UImodule of a printer driver. The data used to populate user interface1800 may originate from a UI GPDD.

User interface 1800 comprises three parts or regions: printer selectionfilter preference 1810, a printer collection list 1820, and a printerfeature/option list 1830.

Printer selection filter preference 1810 defines printer preferences(e.g., those indicated in menu 1100) that are used to exclude someprinters that a user does not intend to print upon. For example, a usermay select Color/BW as a filter, and define only Black/White printers aspossible destination devices. In the depicted example, the printerpreferences are that the printing device must be non-secured, theprinting device must support color printing, that the input bin sizemust be greater than 500 sheets, and the connection type is network.

Printer collection list 1820 lists one or more (or all) printing devicesthat are within a set of possible destination printing devices after theuser's preferences are defined in printer selection filter preference1810. In the depicted example, three printing devices are in printercollection list 1820: Ricoh Aficio MP 3500 PCL6, Ricoh Aficio MP C3500PCL6, and Ricoh Aficio SP 8200DN PCL6.

Printer feature/option list 1830 lists multiple (or all) features andoptions supported by a set of one or more printing devices that aredetermined based on a set of selection preferences selected by a user(and/or by default). In an embodiment, each time a user changes afeature or option from printer feature/option list 1820, the resultingset of features is validated by a printer driver against thecapabilities of potential printing devices (e.g., those indicated in aDriver GPDD). If a printing device does not support the resulting set offeatures, then all of that printing device's features are disabled inprinter feature/option list 1830. However, if there is a printing devicethat does support the resulting set of features, then all of thatprinting device's features are enabled in printer feature/option list1830.

In this example, printer feature/option list 1830 divides printerfeatures into three main types: Paper/Output, Graphic, and DocumentOptions, which include the majority of the printer features, such asSlip Sheet, Output Bin, Staple, Punch, Edge to Edge Print, PrintDensity, and Print Quality.

XVIII. Establishing an Ad-Hoc Communications Link

FIG. 19 is a flow diagram 1900 that depicts a process for establishingan ad-hoc communications link between a mobile client device and anad-hoc printing device. In step 1902, a user moves a client devicewithin range of an ad-hoc printing device. The range may vary dependingupon the particular type of ad-hoc communications that are supported bythe mobile client device and the ad-hoc printing device.

In step 1904, the mobile client device detects the existence of thead-hoc printing device and displays a device icon on the mobile clientdevice to provide a visual indication to the user. In step 1906, theuser selects the device icon to initiate a pairing process between themobile client device and the ad-hoc printing device.

In step 1908, the mobile client device and the ad-hoc printing devicecreate shared information that will be used to establish the ad-hoccommunications link. In the present example, the mobile client deviceand the ad-hoc printing device create a shared PIN. In step 1910, theuser in queried for the shared information via the mobile client deviceor the ad-hoc printing device. For example, a message may be displayedon a user interface of the mobile client device requesting that the userenter the PIN. In step 1912, the user provides the PIN to the mobileclient device or the ad-hoc printing device. In the present example, theuser is queried for the shared PIN. In step 1914, a determination ismade whether the correct PIN was received at either the mobile clientdevice or the ad-hoc printing device. If not, then in step 1916, theuser is prompted to re-enter the PIN. If the correct PIN was entered,then the pairing process is completed in step 1918.

XIX. Implementation Mechanisms

Managing network device configuration data by functional area asdescribed herein is very user friendly and less prone to errors thanprior approaches. Users are informed of their progress on the GUI aseach functional area of configuration data is updated and thenimplemented on a network device. The approach also reduces bandwidthconsumption by allowing only data that has been updated to be suppliedto a network device. The bulk management features simplify and expeditethe editing of existing configuration data and the creation of newconfiguration data.

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

FIG. 20 is a block diagram that depicts an example computer system 2000upon which embodiments may be implemented. Computer system 2000 includesa bus 2002 or other communication mechanism for communicatinginformation, and a processor 2004 coupled with bus 2002 for processinginformation. Computer system 2000 also includes a main memory 2006, suchas a random access memory (RAM) or other dynamic storage device, coupledto bus 2002 for storing information and instructions to be executed byprocessor 2004. Main memory 2006 also may be used for storing temporaryvariables or other intermediate information during execution ofinstructions to be executed by processor 2004. Computer system 2000further includes a read only memory (ROM) 2008 or other static storagedevice coupled to bus 2002 for storing static information andinstructions for processor 2004. A storage device 2010, such as amagnetic disk or optical disk, is provided and coupled to bus 2002 forstoring information and instructions.

Computer system 2000 may be coupled via bus 2002 to a display 2012, suchas a cathode ray tube (CRT), for displaying information to a computeruser. Although bus 2002 is illustrated as a single bus, bus 2002 maycomprise one or more buses. For example, bus 2002 may include withoutlimitation a control bus by which processor 2004 controls other deviceswithin computer system 2000, an address bus by which processor 2004specifies memory locations of instructions for execution, or any othertype of bus for transferring data or signals between components ofcomputer system 2000.

An input device 2014, including alphanumeric and other keys, is coupledto bus 2002 for communicating information and command selections toprocessor 2004. Another type of user input device is cursor control2016, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor2004 and for controlling cursor movement on display 2012. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

Computer system 2000 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic or computer software which, in combination with thecomputer system, causes or programs computer system 2000 to be aspecial-purpose machine. According to one embodiment, those techniquesare performed by computer system 2000 in response to processor 2004executing one or more sequences of one or more instructions contained inmain memory 2006. Such instructions may be read into main memory 2006from another computer-readable medium, such as storage device 2010.Execution of the sequences of instructions contained in main memory 2006causes processor 2004 to perform the process steps described herein. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions to implement the embodiments.Thus, embodiments are not limited to any specific combination ofhardware circuitry and software.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing data that causes a computer to operate ina specific manner. In an embodiment implemented using computer system2000, various computer-readable media are involved, for example, inproviding instructions to processor 2004 for execution. Such a mediummay take many forms, including but not limited to, non-volatile mediaand volatile media. Non-volatile media includes, for example, optical ormagnetic disks, such as storage device 2010. Volatile media includesdynamic memory, such as main memory 2006. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM,any other optical medium, a RAM, a PROM, and EPROM, a FLASH-EPROM, anyother memory chip or memory cartridge, or any other medium from which acomputer can read.

Various forms of computer-readable media may be involved in carrying oneor more sequences of one or more instructions to processor 2004 forexecution. For example, the instructions may initially be carried on amagnetic disk of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 2000 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 2002. Bus 2002 carries the data tomain memory 2006, from which processor 2004 retrieves and executes theinstructions. The instructions received by main memory 2006 mayoptionally be stored on storage device 2010 either before or afterexecution by processor 2004.

Computer system 2000 also includes a communication interface 2018coupled to bus 2002. Communication interface 2018 provides a two-waydata communication coupling to a network link 2020 that is connected toa local network 2022. For example, communication interface 2018 may bean integrated services digital network (ISDN) card or a modem to providea data communication connection to a corresponding type of telephoneline. As another example, communication interface 2018 may be a localarea network (LAN) card to provide a data communication connection to acompatible LAN. Wireless links may also be implemented. In any suchimplementation, communication interface 2018 sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

Network link 2020 typically provides data communication through one ormore networks to other data devices. For example, network link 2020 mayprovide a connection through local network 2022 to a host computer 2024or to data equipment operated by an Internet Service Provider (ISP)2026. ISP 2026 in turn provides data communication services through theworld wide packet data communication network now commonly referred to asthe “Internet” 2028. Local network 2022 and Internet 2028 both useelectrical, electromagnetic or optical signals that carry digital datastreams.

Computer system 2000 can send messages and receive data, includingprogram code, through the network(s), network link 2020 andcommunication interface 2018. In the Internet example, a server 2030might transmit a requested code for an application program throughInternet 2028, ISP 2026, local network 2022 and communication interface2018. The received code may be executed by processor 2004 as it isreceived, and/or stored in storage device 2010, or other non-volatilestorage for later execution.

In the foregoing specification, embodiments have been described withreference to numerous specific details that may vary from implementationto implementation. Thus, the sole and exclusive indicator of what is,and is intended by the applicants to be, the invention is the set ofclaims that issue from this application, in the specific form in whichsuch claims issue, including any subsequent correction. Hence, nolimitation, element, property, feature, advantage or attribute that isnot expressly recited in a claim should limit the scope of such claim inany way. The specification and drawings are, accordingly, to be regardedin an illustrative rather than a restrictive sense.

What is claimed is:
 1. One or more non-transitory computer-readablemedia storing instructions which, when processed by one or moreprocessors, cause: prior to an ad-hoc wireless communications link beingestablished between a mobile client device and a particular ad-hocprinting device, at the mobile client device, generating a print job;and after the ad-hoc wireless communications link is established betweenthe mobile client device and the particular ad-hoc printing device:determining, at the mobile client device, whether the print job iscompatible with the particular ad-hoc printing device, in response todetermining, at the mobile client device, that the print job iscompatible with the particular ad-hoc printing device, then causing theprint job to be transmitted to the particular ad-hoc printing device viathe ad-hoc wireless communications link, and in response to determining,at the mobile client device, that the print job is not compatible withthe particular ad-hoc printing device, then generating, at the mobileclient device, an updated print job by resolving one or moreincompatibilities between the print job and the particular ad-hocprinting device, and causing, at the mobile client device, the updatedprint job to be transmitted to the particular ad-hoc printing device viathe ad-hoc wireless communications link.
 2. The one or morenon-transitory computer-readable media of claim 1, further storingadditional instructions which, when processed by the one or moreprocessors, cause: detecting, at the mobile client device, that an erroron the ad-hoc wireless communications link has prevented the print jobfrom being successfully processed, in response to detecting, at themobile client device, that an error on the ad-hoc wirelesscommunications link has prevented the print job from being successfullyprocessed, then causing one or more of establishing a new ad-hocwireless communications link with the particular ad-hoc printing deviceor establishing an ad-hoc wireless communications link with anotherad-hoc printing device that is different than the particular ad-hocprinting device.
 3. The one or more non-transitory computer-readablemedia of claim 2, further storing additional instructions which, whenprocessed by the one or more processors, cause: at the mobile clientdevice, displaying via a user interface of the mobile client device, oneor more graphical user interface objects that allow a user of the mobileclient device to request an attempt to establish a new ad-hoc wirelesscommunications link with the particular ad-hoc printing device or torequest an attempt to establish an ad-hoc wireless communications linkwith the other ad-hoc wireless communications device.
 4. The one or morenon-transitory computer-readable media of claim 2, further storingadditional instructions which, when processed by the one or moreprocessors, cause: at the mobile client device, after establishing a newad-hoc wireless communications link with the particular ad-hoc printingdevice and prior to causing the print job to again be transmitted to theparticular ad-hoc printing device, determining whether one or morefeatures and options for the print job are currently supported by theparticular ad-hoc printing device; and at the mobile client device,after establishing an ad-hoc wireless communications link with the otherad-hoc printing device that is different than the particular ad-hocprinting device and prior to causing the print job to be transmitted tothe other ad-hoc printing device, determining whether one or morefeatures and options for the print job are currently supported by theother ad-hoc printing device.
 5. The one or more non-transitorycomputer-readable media of claim 1, further storing additionalinstructions which, when processed by the one or more processors, cause:determining, at the mobile client device, whether the print job iscompatible with the particular ad-hoc printing device by determining, atthe mobile client device, whether one or more features and options forthe print job are currently supported by the particular ad-hoc printingdevice.
 6. The one or more non-transitory computer-readable media ofclaim 5, further storing additional instructions which, when processedby the one or more processors, cause: querying, at the mobile clientdevice, the particular ad-hoc printing device to obtain data thatindicates features and options currently supported by the ad-hocprinting device; and comparing, at the mobile client device, thefeatures and options currently supported by the ad-hoc printing deviceto the one or more features and options for the print job.
 7. The one ormore non-transitory computer-readable media of claim 1, wherein: the oneor more incompatibilities between the print job and the particularad-hoc printing device are caused by one or more print tickets thatcorrespond to the print job specifying one or more features and optionsfor processing the print job that are not currently supported by theparticular ad-hoc printing device, and the one or more non-transitorycomputer-readable media further store additional instructions which,when processed by the one or more processors, cause resolving the one ormore incompatibilities between the print job and the particular ad-hocprinting device by: displaying, via a user interface of the mobileclient device, one or more graphical user interface objects that allow auser of the mobile client device to change one or more features andoptions values specified by the one or more print tickets thatcorrespond to the print job.
 8. The one or more non-transitorycomputer-readable media of claim 1, further storing additionalinstructions which, when processed by the one or more processors, cause:displaying, via a user interface of the mobile client device, one ormore graphical user interface objects that correspond to a plurality offeatures and options; receiving, via the user interface of the mobileclient device, a user selection of one or more particular features andoptions for processing the print job on the particular ad-hoc printingdevice; and selecting, at the mobile client device, the particularad-hoc printing device from a plurality of ad-hoc printing devices,based upon a determination that the particular ad-hoc printing devicecurrently supports the one or more particular features and options forprocessing the print job indicated by the user selection.
 9. Anapparatus comprising: one or more processors; and one or more memoriesstoring instructions which, when processed by the one or moreprocessors, causes: prior to an ad-hoc wireless communications linkbeing established between a mobile client device and a particular ad-hocprinting device, at the mobile client device, generating a print job;and after the ad-hoc wireless communications link is established betweenthe mobile client device and the particular ad-hoc printing device:determining, at the mobile client device, whether the print job iscompatible with the particular ad-hoc printing device, in response todetermining, at the mobile client device, that the print job iscompatible with the particular ad-hoc printing device, then causing theprint job to be transmitted to the particular ad-hoc printing device viathe ad-hoc wireless communications link, and in response to determining,at the mobile client device, that the print job is not compatible withthe particular ad-hoc printing device, then generating, at the mobileclient device, an updated print job by resolving one or moreincompatibilities between the print job and the particular ad-hocprinting device, and causing, at the mobile client device, the updatedprint job to be transmitted to the particular ad-hoc printing device viathe ad-hoc wireless communications link.
 10. The apparatus of claim 9,wherein the one or more memories store additional instructions which,when processed by the one or more processors, cause: detecting, at themobile client device, that an error on the ad-hoc wirelesscommunications link has prevented the print job from being successfullyprocessed, in response to detecting, at the mobile client device, thatan error on the ad-hoc wireless communications link has prevented theprint job from being successfully processed, then causing one or more ofestablishing a new ad-hoc wireless communications link with theparticular ad-hoc printing device or establishing an ad-hoc wirelesscommunications link with another ad-hoc printing device that isdifferent than the particular ad-hoc printing device.
 11. The apparatusof claim 10, wherein the one or more memories store additionalinstructions which, when processed by the one or more processors, cause:at the mobile client device, displaying via a user interface of themobile client device, one or more graphical user interface objects thatallow a user of the mobile client device to request an attempt toestablish a new ad-hoc wireless communications link with the particularad-hoc printing device or to request an attempt to establish an ad-hocwireless communications link with the other ad-hoc wirelesscommunications device.
 12. The apparatus of claim 10, wherein the one ormore memories store additional instructions which, when processed by theone or more processors, cause: at the mobile client device, afterestablishing a new ad-hoc wireless communications link with theparticular ad-hoc printing device and prior to causing the print job toagain be transmitted to the particular ad-hoc printing device,determining whether one or more features and options for the print jobare currently supported by the particular ad-hoc printing device; and atthe mobile client device, after establishing an ad-hoc wirelesscommunications link with the other ad-hoc printing device that isdifferent than the particular ad-hoc printing device and prior tocausing the print job to be transmitted to the other ad-hoc printingdevice, determining whether one or more features and options for theprint job are currently supported by the other ad-hoc printing device.13. The apparatus of claim 9, wherein the one or more memories storeadditional instructions which, when processed by the one or moreprocessors, cause: determining, at the mobile client device, whether theprint job is compatible with the particular ad-hoc printing device bydetermining, at the mobile client device, whether one or more featuresand options for the print job are currently supported by the particularad-hoc printing device.
 14. The apparatus of claim 13, wherein the oneor more memories store additional instructions which, when processed bythe one or more processors, cause: querying, at the mobile clientdevice, the particular ad-hoc printing device to obtain data thatindicates features and options currently supported by the ad-hocprinting device; and comparing, at the mobile client device, thefeatures and options currently supported by the ad-hoc printing deviceto the one or more features and options for the print job.
 15. Theapparatus of claim 9, wherein: the one or more incompatibilities betweenthe print job and the particular ad-hoc printing device are caused byone or more print tickets that correspond to the print job specifyingone or more features and options for processing the print job that arenot currently supported by the particular ad-hoc printing device, andthe one or more non-transitory computer-readable media further storeadditional instructions which, when processed by the one or moreprocessors, cause resolving the one or more incompatibilities betweenthe print job and the particular ad-hoc printing device by: displaying,via a user interface of the mobile client device, one or more graphicaluser interface objects that allow a user of the mobile client device tochange one or more features and options values specified by the one ormore print tickets that correspond to the print job.
 16. The apparatusof claim 9, wherein the one or more memories store additionalinstructions which, when processed by the one or more processors, cause:displaying, via a user interface of the mobile client device, one ormore graphical user interface objects that correspond to a plurality offeatures and options; receiving, via the user interface of the mobileclient device, a user selection of one or more particular features andoptions for processing the print job on the particular ad-hoc printingdevice; and selecting, at the mobile client device, the particularad-hoc printing device from a plurality of ad-hoc printing devices,based upon a determination that the particular ad-hoc printing devicecurrently supports the one or more particular features and options forprocessing the print job indicated by the user selection.
 17. Acomputer-implemented method comprising: prior to an ad-hoc wirelesscommunications link being established between a mobile client device anda particular ad-hoc printing device, at the mobile client device,generating a print job; and after the ad-hoc wireless communicationslink is established between the mobile client device and the particularad-hoc printing device: determining, at the mobile client device,whether the print job is compatible with the particular ad-hoc printingdevice, in response to determining, at the mobile client device, thatthe print job is compatible with the particular ad-hoc printing device,then causing the print job to be transmitted to the particular ad-hocprinting device via the ad-hoc wireless communications link, and inresponse to determining, at the mobile client device, that the print jobis not compatible with the particular ad-hoc printing device, thengenerating, at the mobile client device, an updated print job byresolving one or more incompatibilities between the print job and theparticular ad-hoc printing device, and causing, at the mobile clientdevice, the updated print job to be transmitted to the particular ad-hocprinting device via the ad-hoc wireless communications link.
 18. Thecomputer-implemented method of claim 17, further comprising: detecting,at the mobile client device, that an error on the ad-hoc wirelesscommunications link has prevented the print job from being successfullyprocessed, in response to detecting, at the mobile client device, thatan error on the ad-hoc wireless communications link has prevented theprint job from being successfully processed, then causing one or more ofestablishing a new ad-hoc wireless communications link with theparticular ad-hoc printing device or establishing an ad-hoc wirelesscommunications link with another ad-hoc printing device that isdifferent than the particular ad-hoc printing device.
 19. Thecomputer-implemented method of claim 17, wherein: the one or moreincompatibilities between the print job and the particular ad-hocprinting device are caused by one or more print tickets that correspondto the print job specifying one or more features and options forprocessing the print job that are not currently supported by theparticular ad-hoc printing device, and the computer-implemented methodfurther comprises resolving the one or more incompatibilities betweenthe print job and the particular ad-hoc printing device by: displaying,via a user interface of the mobile client device, one or more graphicaluser interface objects that allow a user of the mobile client device tochange one or more features and options values specified by the one ormore print tickets that correspond to the print job.
 20. Thecomputer-implemented method of claim 17, further comprising: displaying,via a user interface of the mobile client device, one or more graphicaluser interface objects that correspond to a plurality of features andoptions; receiving, via the user interface of the mobile client device,a user selection of one or more particular features and options forprocessing the print job on the particular ad-hoc printing device; andselecting, at the mobile client device, the particular ad-hoc printingdevice from a plurality of ad-hoc printing devices, based upon adetermination that the particular ad-hoc printing device currentlysupports the one or more particular features and options for processingthe print job indicated by the user selection.